Ivan Gretsky

🐞Bug report confirmed (from my side)))

Yerd looks like really cool! It is written in Rust, so has all the hype needed! The Windows version is planned for end of August as I can see from their roadmap. So have to wait a bit to try as Windows is still my primary workhorse. The other thing is it doesn't seem to have Apache. So it might be not so easy to use it with ProcessWire. Flyenv is in TypeScript, so less hype here. But it has an MCP for AI. Not sure it is needed on that level. But still trendy. End it offers support for not only PHP but some other languages and runtimes. And it has Apache. So must be suitable for ProcessWire. I have started to use mise for CLI tooling and as a simple task runner. I have found some cool CLI tools using it. End it is able to easily install many of those new shiny AI agent tools in the project scope. But I do not think it can handle environment for a PHP project like ProcessWire. At least I do not know how to do it. Really cool topic by the way! So many tools emerge nowadays! So many new possibilities that seemed hard and almost impossible for a solo dev or small team just a few years ago.

Wow, @maximus! This is a great idea for a module! I can see it is on LQRS' 404 too. Going to try this! A few little glitches I've spotted on LQRS: The module fires on every search request and outputs the generated content at the top. Even when there are results. That might be distracting users from real pages. LLM hallucinates links to non-existing pages when I ask for them directions based on my request. Might tell it to only give existing links.

Just tried Kimi K3 with Kilo via Openrouter on a rather small task. But with a lot of custom code and hooks to find and read. It dug deep, tested well, used agent tools like it should and wrote in align with all the rules I gave it. But spent a lot of time. A good one but might be an overkill for easy stuff.

Wow! Excited to be on the same continent with you! Welcome and have fun!) What should one do to get this level of promotion 😆 ?!

Thanks @gebeer! Love is something that unites people. There are different kinds of love and love to a PW module is certainly a valid one. Any kind of love is IMHO an expression of openness to something outside yourself. Willingness to accept and even incorporate something seemingly foreign. Another human being. Another style of writing code. Another vision of the future. Another business model. Another opinion. My relationships with RockMigrations is too of hard road to love. I didn't accept its bloated nature and desire to bring the whole Rock infrastructure with it)) But I learned the way to ignore and work around those. And even built a complex PW scaffolding script using this super module. And I have met its author, a passionate man and developer. I am writing this knowing that Bernhard has almost quit the PW community. I know what brought him to this decision. And that was kind of a lack of love. So I think this post is a great one and I totally agree with it 100%. And I wish that everyone here, including @ryan, @bernhard, @Pete (and actually everyone) would consider finding time, energy... humility and open mindedness to give ProcessWire and its daughter RockMigrations a bit more family love. A love that would raise them both to a greater future. A love that no AI could ever give. A love that is the core of this community which has so much unrealized potential. Peace ☮️

IMHO the categories do not mean much nowadays. At least for an experienced forum user. I never go to categories list first but always start with recently updated topics. Most of the time I do not even know the category the post is in. And when I need to find something I search. I go to the category list when I want to get help on modules, especially Ryan's pro modules. The other case is when I create a new post. And that is when it gets confusing. I can never decide where to put it. I can see not difference between Getting started, General support, API and templates and even Modules/Plugins as any of my questions usually relates to all of them somehow. Not to say there is not such thing as "plugin" in PW. It all might seem quite different for a newcomer though. And if we know for sure that affects the community friendliness we should change that. But I actually do not know how. Just maybe some overenthusiastic forum member can push the changes. Or AI will help) Anyway, anything concerning the forums mechanics should at least mention @Pete))) P.S. I am pretty sure forum engines have some cool features nowadays, like tagging and more. And even though the forum as a communication format seem to vanish, we still can try to use more of those new features here. As we, old school nerds are still using 'em)

What I really like about this coming of AI to ProcessWire is the discussion, the human communication it brings. Ryan is active and passionate in the forums like we hasn't been for a while. We all are once again experimenting and regaining faith in that our beloved computer thing will not stagnate but make its way onto the next level. I do not want that to end in no way. The same time I am too a bit afraid of AI lowering the quality of content here and the product itself. Too much enthusiastic awe and uncontrolled trust in AI could lead us there. So our collective goal is to balance things up. I can see you Ryan delighted to share the cool things you've built with AI with us all. And I personally want to read those blog posts. But if they get published alongside with your content unchecked or even checked but still containing some mistakes, that could not only turn away human readers, but also be the source for future less good answers from AI itself, as it is reading its own writings for sure. We could create a dedicated site section or dedicated forum section for AI-written articles. And maybe make it non-indexable by search engines. We should add an explicit warning like @Peter Knight suggested for sure. And maybe propose a game/challenge for the forum members to read them critically and comment on them. Maybe establish a workflow for AI to respond to those comments and to correct the text. We can really come up with something quite good in the end. Not only better texts that could be published. But also smarter AI and a more cohesive community. What do you think? P.S. We probably should also limit the amount of those articles. Humans are not as capable of reading as AI is of writing. The new era of a consumer rule is already here - it is harder and harder to find a good consumer for your stuff, especially something like a blog post)))

ProcessWire now has a native cli installer.

I assume you want those other RM types that should not be editable by the user with the given role still to be shown in admin, but with all their fields being disabled. The best way to achieve this is via hooks. Look here or search for similar topics for inspiration. Check RestrictRepeaterMatrix's source code for another example. You need to get the InputfieldRepeaterMatrix field at some point (maybe after the renderReadyHook method), foreach through the blocks and change their fields' output based on your conditions. Sorry for no ready-to-copy-and-paste code))

I remember that there were some attempts to create courses on PW, but none of them really stuck in my memory. I think it is better to make one's way through tutorials and read through the docs. There are some videos that can be useful. These come to mind: https://www.youtube.com/watch?v=IHqnLQy9R1A - a really dated walkthrough I have once started with; everything looks different but the essence is the same) https://www.youtube.com/playlist?list=PLOrdUWNK38ibz8U_5Vq4zSPZfvFKzUuiT - a comparaison to WP

Reading through the commits log is like never before. I guess we are going to have a lot of cool stuff we were waiting for happening soon.

Cool! Why a zip file and not a repo?

Good day! I have a module that sets a url hook. But then I have code in site/ready.php that stops page rendering process under certain conditions based on a page being viewed. So I need to modify that condition to include all url/path hooks. How do I do it? I thought of setting a custom $config variable. Or checking for $config->requestPath(). But maybe there is something universal?

@maximus Seeing the speed with which you produce new cool modules just maybe you could come up with a custom theme css pretty quickly: - https://forum.nette.org/cs/31690-dark-mode-pro-tracy-css (translate from Czech) - https://github.com/nette/tracy/blob/ab7b1d19c0de130bed6de5b30c9ad7884131b465/src/Tracy/Debugger.php#L107-L111 It is already possible to change the debugger output to dark natively like this Debugger::$dumpTheme = 'dark'; (https://tracy.nette.org/en/dumper), but that is already by default, as I understand.